Thread: struct mystruct mystruct = { item1: value, . . .

Hmm, something else I didn't know -- is _THIS_ in the standard?

Code:

struct mystruct {
        int item1, item2, item3, item4, item5, item10; // I think you get the point
} mystruct = {
        item1: 1,
        item2: 2,
        item5: 5,
        item4: 4,
};

Now, using the above struct definition, I have done this many times in the past:

Code:

struct mystruct mystruct = {
        .item1 = 1,
        .item2 = 2,
};

but the use of the colon is something I've never seen before. It this compiler dependent?


Thanks again!

Man, you think you know a language fairly well, then all sorts of new things start happening.

At first, I thought Quzah was on to something, that item1: is being treated as a label. But then I wrote this sample program to test it out. Run it and look at the output. It initializes the struct properly.

Code:

#include <stdio.h>

struct mystruct {
    int item1, item2, item3, item4, item5, item10; // I think you get the point
} mystruct = {
       item1: 1,
       item2: 2,
       item5: 5,
       item4: 4,
};

int main(void)
{
    printf("mystruct:\n");
    printf("\titem1  %d\n", mystruct.item1);
    printf("\titem2  %d\n", mystruct.item2);
    printf("\titem3  %d\n", mystruct.item3);
    printf("\titem4  %d\n", mystruct.item4);
    printf("\titem5  %d\n", mystruct.item5);
    printf("\titem10 %d\n", mystruct.item10);

    return 0;
}

It compiled with "gcc -Wall main.c" just fine. Then I compiled it with "gcc -Wall -pedantic main.c" and got the following errors
main.c:6: warning: obsolete use of designated initializer with ‘:’
main.c:7: warning: obsolete use of designated initializer with ‘:’
main.c:8: warning: obsolete use of designated initializer with ‘:’
main.c:9: warning: obsolete use of designated initializer with ‘:’

Looks like some outdated syntax.

Code:

struct mystruct mystruct = {
        .item1 = 1,
        .item2 = 2,
};

http://publib.boulder.ibm.com/infoce...esignators.htm
For the first one, i don't think it's standard.

I compiled it with PellesC....

Code:

Building main.obj.
D:\Programming\Experiments\dosprog\main.c(9): error #2048: Undeclared identifier 'item1'.
D:\Programming\Experiments\dosprog\main.c(9): error #2001: Syntax error: expected '}' but found ':'.
D:\Programming\Experiments\dosprog\main.c(13): error #2069: Initializer must be constant.
*** Error code: 1 ***
Done.

It's just bad code....

Code:

struct mystruct {
    int item1, item2, item3, item4, item5, item10; // I think you get the point
} mystruct = {
       item1: 1,
       item2: 2,
       item5: 5,
       item4: 4,
};

you can define a struct like:

Code:

struct mystruct {
       item1: 1,
       item2: 2,
       item5: 5,
       item4: 4,
};

can't initialize it that way

Originally Posted by Salem

We do have a sticky thread ....
C Draft Standards

Doh! I forgot about that.

Didn't, however, find anything about initialization of structure elements using ':'. In fact, the only place I found ':' mentioned was under the labels section.

Based upon the compiler error mention above, however, it appears to be something from the original language. That being said, I'm changing it to the latest format for init.

Thanks for the comments!

Originally Posted by Jesius

Code:

struct mystruct {
    int item1, item2, item3, item4, item5, item10; // I think you get the point
} mystruct = {
       item1: 1,
       item2: 2,
       item5: 5,
       item4: 4,
};

you can define a struct like:

Code:

struct mystruct {
       item1: 1,
       item2: 2,
       item5: 5,
       item4: 4,
};

can't initialize it that way

You are wrong. I can init it this way using GCC. In fact, either way works on any of the GCC's that I have (I have 5).

Originally Posted by Kennedy

You are wrong. I can init it this way using GCC. In fact, either way works on any of the GCC's that I have (I have 5).

Do you have your errors and warnings turned off?

Message 1 is absolutely not standard C .... in fact I'm surprised GCC will compile it, PellesC won't and it's pretty big on standards.

Originally Posted by CommonTater

Do you have your errors and warnings turned off?

Message 1 is absolutely not standard C .... in fact I'm surprised GCC will compile it, PellesC won't and it's pretty big on standards.

The build system for the kernel enables _ALL_ warnings and treats all warnings as errors (at least with 2.6.36.1 this is the case -- This is something that Linus has been pushing for for many years, though I don't know when he started the warnings as errors bit and why you can see many Linus melt downs on LKML if you search for "warning bomb")

Originally Posted by itsme86

It looks like a GCC extension: GCC's website

Hmmm. Something seems strange to me. The code that I'm looking at is an init of the fsops struct. I know that llseek is first, though llseek was not configured in this init, but the init does work. I have even tried it with a simple helloworld and it does what it is "supposed" to do. . .

Like I said, I'm changing this code since it is, at a minimum, confusing.

Andy